Hello, Using Exchange 2010 SP2 I setup my send conector to go through a third party provider (dyndns) before reaching Internet to avoid Spam detection and all. Unfortunatly I have a daily limit that I cannot increase. If I create a second connector, how will Exchange 2010 react? will it split emails to the two connectors without other problem or will it always use one of them and use the second only if the first one stops responding?

Hi, you are able to create mor then one sendconnector and use the Address Space and Cost Attribute in order to deperate mails processed by the connectors. But In not sure if this is the solution for you. Please let me know some more details about your limitations. Is it a limitation configured by your provider? And what role plays dnydns in sending mails? regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

If you create a second connector which is identical to the original in everything but smart host then Exchange will round robin the traffic, so it will be roughly 50/50. What happens when you reach your limit on the other service is hard to say, as it depends on how they reject the email. Are you not on a static IP address then? Does your ISP not provide an SMTP server you can route email through? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

On Thu, 29 Mar 2012 17:30:49 +0000, Jeremy_E wrote: >Using Exchange 2010 SP2 I setup my send conector to go through a third party provider (dyndns) before reaching Internet to avoid Spam detection and all. > >Unfortunatly I have a daily limit that I cannot increase. Yes, you can. It just costs more. :-) Since you're using dyndns as a SMTP relay, and you're constrained by their message limits, it's pretty safe to assume that you aren't a volume sender. The likleyhood of your being placed on any DNSBLs is pretty low -- unless you're also using a dynamic IP address. >If I create a second connector, how will Exchange 2010 react? Usually not the way you'd expect. >will it split emails to the two connectors Provided they have the same set of values in the address space and they have the same cost assigned, yes. But they'll both use the same IP address, so if you get yourself on a DNSBL you'll still be out of luck. >without other problem or will it always use one of them and use the second only if the first one stops responding? DYNDNS isn't going to "stop responding", it's going to send 4xx status codes which will just put the messages into a retry state until the next day (when dyndns resets your quota). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 29 Mar 2012 17:30:49 +0000, Jeremy_E wrote: >Using Exchange 2010 SP2 I setup my send conector to go through a third party provider (dyndns) before reaching Internet to avoid Spam detection and all. > >Unfortunatly I have a daily limit that I cannot increase. Yes, you can. It just costs more. :-) Since you're using dyndns as a SMTP relay, and you're constrained by their message limits, it's pretty safe to assume that you aren't a volume sender. The likleyhood of your being placed on any DNSBLs is pretty low -- unless you're also using a dynamic IP address. >If I create a second connector, how will Exchange 2010 react? Usually not the way you'd expect. >will it split emails to the two connectors Provided they have the same set of values in the address space and they have the same cost assigned, yes. But they'll both use the same IP address, so if you get yourself on a DNSBL you'll still be out of luck. >without other problem or will it always use one of them and use the second only if the first one stops responding? DYNDNS isn't going to "stop responding", it's going to send 4xx status codes which will just put the messages into a retry state until the next day (when dyndns resets your quota). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

hi, How about your issue now, any update? Please remember to mark as answer. thanks,CastinLu TechNet Community Support